Fix Portable Black Screen (Missing Files & Protocol) - #28
Fix Portable Black Screen (Missing Files & Protocol)#28google-labs-jules[bot] wants to merge 1 commit into
Conversation
…cking; improve login UI
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
This submission completely resolves the "Black Screen" issue in Portable builds by addressing the root cause (missing build artifacts) and implementing a robust custom protocol for asset loading.
Critical Fixes:
"files": ["dist-electron", "dist"]topackage.json. This forceselectron-builderto include the frontend assets in the package, which were previously excluded becausedist/is in.gitignore. This was the primary cause of thechrome-error://chromewebdata/black screen.app://): Replacedfile://loading with a customapp://git-watcher/protocol. This bypasses security restrictions and path resolution issues common in portable environments, ensuring assets load reliably from the ASAR archive.gitoperations, eliminating theGitError: cannot lock refandPermission deniederrors seen in the logs.UI & UX Improvements:
HYPOTHESES.mddetailing the investigation into the black screen issue.Verification:
PR created automatically by Jules for task 11562340079226017196 started by @Javaec